o Administrivia, problems with the archive, and problems with your
  submission or subscription go to info-mac-request@sumex.stanford.edu.
  Messages to be included in digests or in the archive go to
  info-mac@sumex.stanford.edu.
  Programs to be announced in digests and included in the archive go to
  macgifts@sumex.stanford.edu.

o We do not accept commercial announcements of products or services. However,
  we welcome demonstration copies of commercial products.

o If you're on Bitnet, you can also send to info-mac@RICEVM1 if that's easier
  for your system.

o We prefer to have submissions mailed to macgifts rather than posted to
  comp.sys.mac.digest because often we receive many copies of a single posting
  to that Usenet group, or the news software introduces extra headers
  which clutter up the digest. The mail is more reliable.

o If you submit a letter or binary and later decide to retract it (or
  replace it with another message), you must send a note to info-mac-request.
  Do NOT mail to info-mac because we usually read that file in chronological
  order and will likely miss your subsequent correction.

o Please keep signatures to a minimum. Long ones are frustrating to those
  of us on 1200 baud modem connections! 80 characters is our preferred
  limit, although 160 characters are OK if the signature is just-the-facts.

o To send us a binary, first compress and BinHex your file, and then write
  a text blurb to be put in the digests announcing your file. Send the text
  and the BinHexed file to us as ONE message if at all possible.  Remember,
  use a compression program to help us save on disk space. To avoid
  frustrating our users, please make sure that we have a copy of the
  compression program in the archive. Note that text files are not considered
  binaries and hence do not need to be binhexed. Also, please send only one
  attachment per email message.

o To submit a file greater than 800K, or to avoid submitting by (and
  segmenting for) email, send email describing the file to
  backmod@sumex-aim.stanford.edu and upload it to:
  ftp://daemon.ncsa.uiuc.edu//Incoming
  As with emailed submissions, non-text files must be binhexed.

o Please don't be cute with the (This file must be converted with BinHex 4.0)
  line. If you change the words, it messes up our automatic software.

o Describe your binary posting accurately, but be CONCISE.  More detailed
  information belongs in a document attached to your posting. Binaries that
  do not include a description will not be accepted in most cases.

o Use version numbers to keep binary updates in order. If you are posting
  a minor update to a very large file, consider using the UpdateMaker program
  (in /disk) to create a small update document instead of making people
  download the whole thing over again. However, if the resulting update
  file's size is a significant percentage of the size of the original,
  say over 25%, please just send a complete new package.

o Choose a name for your binary - the shorter, the better. This name should
  be the Subject: of your mailing. If it's not obvious, tell us which
  directory you think it should go in. And don't make the subject line
  too long; keep it less than 50 characters or so. If possible, also include
  a three to five word description in the subject line.

o Don't assume a reader is familiar with a binary.  Updates still
  should contain a short description of what a program does.

o Please post programs only if you feel they are of general benefit to
  the Macintosh community.  This will help reduce the load on our end.

o Check your binaries for problems before sending them.  Make sure that
  they are complete and virus-free. Use the latest version of Disinfectant to
  check for the known types of infection. Disinfectant is located in our vir/
  directory.

o If possible, specify whether your binary may be included on the
  commercially available CD-ROM of the archives.

Thank you for your interest and help.

The Info-Mac Moderators
info-mac-request@sumex.stanford.edu